[AutoPR azure-mgmt-qumulo]-generated-from-SDK Generation - Python-6457554#47566
[AutoPR azure-mgmt-qumulo]-generated-from-SDK Generation - Python-6457554#47566azure-sdk wants to merge 1 commit into
Conversation
…tspconfig.yaml', SDK Release Type: stable, and CommitSHA: '31221e37affcbc82e521758d6d3dde7c97526ecd' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6457554 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release.
There was a problem hiding this comment.
Pull request overview
This is an automated regeneration (AutoPR) of the management-plane package azure-mgmt-qumulo, migrating it from the legacy AutoRest code generator to the new TypeSpec/Python (DPG) code generator and updating the service API version from 2024-06-19 to 2026-04-16. It modernizes packaging (drops setup.py/sdk_packaging.toml in favor of pyproject.toml), raises the minimum Python to 3.10, and refreshes generated models, clients, samples, and tests.
Changes:
- Migrates client/models/operations to the TypeSpec DPG generator (nested
propertiesmodels,send_requestexposed publicly,cloud_setting/get_arm_endpointsendpoint handling). - Modernizes packaging metadata (
pyproject.toml, removessetup.py,sdk_packaging.toml,_meta.json; adds_metadata.json,apiview-properties.json,api.md) and bumps version to 2.1.0. - Updates README and samples to Python 3.10+ / Microsoft Entra wording.
Reviewed changes
Copilot reviewed 62 out of 62 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| sdk/qumulo/.../CHANGELOG.md | New 2.1.0 entry — flagged: omits breaking model restructuring and likely needs a major bump |
| sdk/qumulo/.../azure/mgmt/qumulo/_version.py | Version bumped 2.0.0 → 2.1.0 (matches CHANGELOG) |
| sdk/qumulo/.../pyproject.toml | Adds full build/project metadata; stability flags and Python ≥3.10 consistent with stable status |
| sdk/qumulo/.../setup.py, sdk_packaging.toml, _meta.json | Removed legacy packaging/metadata files |
| sdk/qumulo/.../azure/mgmt/qumulo/_client.py, aio/_client.py | New endpoint/cloud_setting handling, public send_request; signature order (credential, subscription_id, base_url) correct |
| sdk/qumulo/.../README.md | Python 3.10+ and Microsoft Entra wording updates |
| sdk/qumulo/.../MANIFEST.in, tsp-location.yaml, _metadata.json, api.md, apiview-properties.json, api.metadata.yml | Packaging/spec-tracking and API surface metadata refresh |
| sdk/qumulo/.../tests/*_test.py | Trivial whitespace/formatting only |
| sdk/qumulo/.../azure/mgmt/qumulo/** (models, enums, operations, config, init) | Generated source regenerated to DPG; reviewed per mgmt rules (source under azure/mgmt/** other than _client.py not individually reviewed) |
| sdk/qumulo/.../generated_samples/, generated_tests/ | Generated samples/tests refreshed (excluded from review per mgmt rules) |
The main substantive concern is that the regeneration moves FileSystemResource's service fields into a nested properties object and removes previously public models (FileSystemResourceListResult, OperationListResult) — breaking changes for a released 2.x package — yet the CHANGELOG documents only "Features Added" with a minor version bump. This warrants human confirmation of the version and changelog before release.
| ## 2.1.0 (2026-06-19) | ||
|
|
||
| ### Features Added | ||
|
|
||
| - Client `QumuloMgmtClient` added parameter `cloud_setting` in method `__init__` | ||
| - Client `QumuloMgmtClient` added method `send_request` | ||
| - Model `FileSystemResourceUpdateProperties` added property `performance_tier` |
Configurations: 'specification/liftrqumulo/Qumulo.Storage.Management/tspconfig.yaml', SDK Release Type: stable, and CommitSHA: '31221e37affcbc82e521758d6d3dde7c97526ecd' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6457554 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. Release plan link: https://azsdk-releaseplan-dashboard-hveph5aqhhcfhtgu.westus-01.azurewebsites.net/?releaseplan=35035 Submitted by: kaurnavjot@microsoft.com
Release Plan Details